Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[vRealize Automation Cloud] Preparing a vSphere VM to Receive a cloud-init Script (76346)

Last Updated: 3/4/2020Categories: How toTotal Views: 5602Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

A guide on how to setup a Debian-based Linux VM so that cloud-init scripts can be passed through vRealize Automation Cloud.

Impact / Risks

This guide is only applicable to Debian-based Linux VMs.

Resolution

The first step in preparing a VM to receive a cloud-init scripts is to make sure that the cloud-init package has been installed on the template VM that will be used. Certain distros will include the cloud-init package with the OS ISO, whereas others require a manual installation.

For Debian Based systems:

​sudo apt-get -y update

​sudo apt-get -y install cloud-init

Once the package is installed, reconfigure the package so that it only accepts inputs from OVF sources. This step will greatly decrease the time required to execute the cloud-init script.

Execute sudo dpkg-reconfigure cloud-init

At this point, finalize the template VM's state by installing any additional packages or making any required configuration changes to the OS.

The final step before converting to a template is to clean out the cloud-init logs.

Execute sudo cloud-init clean --logs.

Power off the VM, right click edit settings, change the CD/DVD drive 1 to Client Device with Device Mode Passthrough CD-ROM

The final step is to convert the VM to a template to be used for vRAC deployments.

With all of these steps followed, the VM is now prepared to receive cloud-init configurations from vRAC.

Related Information

Cloud-init examples

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vRealize Operations Manager での障害アラートの管理 (74781)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

VMware Aria Automation

Related Versions:

Take Our Survey

Support Assistant